Open/ClosedPrinciple

2018年5月17日 — 對於擴展是開放的— 當需求變更時模組行為可以新增的; 對於修改是封閉的— 當進行擴展時，不需修改既有的程式碼. 講白一點.

2024年1月8日 — As the name suggests, this principle states that software entities should be open for extension, but closed for modification. As a result, when ...

2023年2月22日 — The open-closed principle states that software entities (classes, modules, functions, and so on) should be open for extension, but closed for ...

2018年3月28日 — The Open/Closed Principle is one of five design principles for object-oriented software development described by Robert C. Martin. They are best ...

簡單來說，就是當系統需要被擴充時，應該藉由新增新的程式碼來擴充新功能，而非修改原本的程式碼來擴充新功能。

外部連結 編輯 · The Open/Closed Principle: Concerns about Change in Software Design.

2020年8月25日 — 但在Uncle Bob 的文章中，他定義為： You should be able to extend the behavior of a system without having to modify that system.

In object-oriented programming, the open–closed principle (OCP) states software entities (classes, modules, functions, etc.) should be open for extension, ...

2020年3月19日 — Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification. 你在講啥開放 ...

2020年9月11日 — 定義. Software entities like classes, modules and functions should be open for extension but closed for modifications.